fix(deps): bump supported Go versions to 1.27.0 and 1.26.7 - #837
Merged
Conversation
![cursor[bot]](https://avatars.githubusercontent.com/in/1210556?s=60&v=4){kind=small}
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes using default effort and found 1 potential issue.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 3e43f98. Configure here.
github-actions
Bot
force-pushed
the
launchdarklyreleasebot/update-to-go1.27.0-
branch
from
August 21, 2026 17:08
3e43f98 to
5b575d6
Compare
keelerm84
approved these changes
Aug 26, 2026
github-actions
Bot
force-pushed
the
launchdarklyreleasebot/update-to-go1.27.0-
branch
from
August 26, 2026 17:56
308c1df to
3db9906
Compare
golangci-lint v2.11.1 is built with go1.26, so it panics while
typechecking go1.27 stdlib sources:
panic: file requires newer Go version go1.27 (application built with go1.26)
This fails every Go 1.27.0 leg of the CI matrix in `make lint`, before
the tests get a chance to run. v2.13.0 added go1.27 support and v2.13.1
is itself built with go1.27.0.
Also pin the installer to the version tag rather than master. The master
copy of install.sh is regressed for v2.13.0+: that release added
.sbom.json entries to checksums.txt, and master's unanchored
`grep "${BASENAME}"` matches both the tarball line and its
.tar.gz.sbom.json line, yielding a two-value expected hash that can
never verify. The tagged installer anchors the grep and works.
Finally, drop two //nolint:gosec directives that gosec v2.13.1 no longer
needs -- nolintlint fails the build on unused directives.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
It's time to update Relay's supported Go versions, due to a recent upstream Go release.
The Go major release cadence is ~every 6 months; the two most recent major versions are supported.
Note that between major releases, the Go team often ships multiple minor versions.
This PR's change was generated by running:
git commit -m "run ci" --allow-empty && git push)Note
Overview
Updates Relay’s supported Go toolchain to 1.27.0 (latest) and 1.26.7 (penultimate) in
.github/variables/go-versions.env, which drives the CI Go version matrix.The standalone Docker builder image moves to
golang:1.27.0-alpine3.24. golangci-lint is bumped to v2.13.1, and the Makefile now downloadsinstall.shfrom the matching release tag instead ofmaster.Two gosec
nolintsuppressions are removed inserver.go(TLSMinVersion) andautoconfigcache/store.go(context.WithCancel)—behavior is unchanged; this aligns with the newer linter.Reviewed by Cursor Bugbot for commit d4e0bc7. Bugbot is set up for automated code reviews on this repo. Configure here.